home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
BBS Toolkit
/
BBS Toolkit.iso
/
wildcat
/
netbull.zip
/
NETBULL.CFG
< prev
next >
Wrap
Text File
|
1992-11-26
|
6KB
|
156 lines
BBSNAME=The Charlatan's Cabin BBS
BULLETIN=C:\WC30\BULL\BULL43.BBS /@CODE /@CLS
HELLO=C:\WC30\DISP\HELLO8.BBS /@CODE /@PAUSE
TOMCAT=C:\WC30\DISP\TOMCAT.BBS
BULLETIN=C:\WC30\NETMAIL.LST
HIGHLIGHT=30-33, 95-101
EXCLUDE=0-10,22,35-70
LOGFILE=C:\WC30\TNET.LOG
LOGTYPE=TNET
REFERENCE=NONE
HUBID=MOGUR
NETNAME=NorthAmeriNet
LOGFILE=C:\WC30\TNET.LOG
LOGTYPE=TNET
REFERENCE=NONE
HUBID=PANASIA
NETNAME=The Intelec(tm) Network
LOGFILE=C:\WC30\TNET.LOG
LOGTYPE=TNET
REFERENCE=NONE
HUBID=HOTLINE
NETNAME=The SmartNet Network
LOGFILE=C:\PCRELAY\RELAY.LOG
LOGTYPE=PCRELAY
REFERENCE=C:\PCRELAY\RELAY.REF
HUBID=NONE
NETNAME=RelayNet International Mail Exchange
LOGFILE=C:\WC30\WM.LOG
LOGTYPE=WILDMAIL
REFERENCE=C:\WC30\AREAS.BBS
HUBID=1:268/302
NETNAME=Fido Mail
LOGFILE=C:\WC30\WM.LOG
LOGTYPE=WILDMAIL
REFERENCE=C:\WC30\AREAS.BBS
HUBID=86:8012/3
NETNAME=ToadNet Mail
LOGFILE=C:\WC30\WM.LOG
LOGTYPE=WILDMAIL
REFERENCE=C:\WC30\AREAS.BBS
HUBID=1:282/85
NETNAME=Prowl Mail
LOGFILE=C:\WC30\WM.LOG
LOGTYPE=WILDMAIL
REFERENCE=C:\WC30\AREAS.BBS
HUBID=230:230/1
NETNAME=CRNet Mail
LOGFILE=C:\POSTLINK\POSTLINK.LOG
LOGTYPE=POSTLINK
REFERENCE=D:\POSTLINK\CONFLST.NET
HUBID=NONE
NETNAME=RelayNet International Mail Exchange
===============================================================================
|Explanation of the configuration options:
|
|The BBSNAME= is the name of your BBS as you'd like it to appear in the display
|files.
|
|You may specify up to 19 output files in any combination of the three
|available types: BULLETIN=, HELLO=, and TOMCAT= .
|
|Each file can take one of three forms: If the line begins with HELLO=,
|then the output will be a brief summary of transfer activity on the day
|the last successful transfers were run. If the line begins with BULLETIN=,
|then it will be a full listing of activity over the past 4 days, ending
|with the date of the last successful transfer. Finally, if the line begins
|with TOMCAT=, it will generate a Tomcat! opening screen with a brief summary
|of transfer activity. If you're using Tomcat! 3.01 or later, this screen will
|be displayed each time Tomcat! is started. It includes the official Tomcat!
|kitty character, used with Greg Hewgill's permission.
|
|Three SWITCHES may be added to each file line ... Inserting the /@CODE switch
|will produce Wildcat! 3.0 compatible color codes, which will automatically
|be filtered out by Wildcat! 3.0 if the caller is not color-capable. Thus,
|only ONE output file is needed for your COLOR and MONO callers.
|
|The /ANSI switch will insert standard ANSI color codes, and these display
|files should ONLY be used for color applications, such as earlier versions of
|Wildcat! BBS software, where .SCR files are COLOR and .BBS files are ASCII. In
|that case, you'd want to produce both a .BBS and a .SCR version of each file.
|
|DON'T use /ANSI and /@CODE on the same line. You'll confuse me.
|
|You may also add a /@CLS switch, which will add the appropriate clear screen
|code at the beginning of the file. If no color switch is indicated, the /CLS
|will generate a formfeed (ASCII 12), or if there is a color flag, then the
|clear screen code will be appropriate to the selected format.
|
|You may also place a /@PAUSE switch on the line, which will insert the Wildcat!
|@PAUSE@ code at the end of the file. This option will be ignored if a Tomcat!
|file is specified, but will be added to the end of a HELLO or BULLETIN file if
|requested.
|
|HIGHLIGHT= is an optional list of conference names you would like highlighted
|in the color display files. No highlighting will be performed in the ASCII
|(non-colorized) files. You may enter individual areas separated by commas,
|or ranges of areas separated by a hyphen, for example:
|HIGHLIGHT=0-3,35,38,101-110,124
|
|
|EXCLUDE= is an optional list of conference names you would like EXCLUDEed
|in the display files. You may enter individual areas separated by commas,
|or ranges of areas separated by a hyphen, for example:
|EXCLUDE=0-10,22,35-70
|
|
|LOG file specifications:
|========================
|
| LOGFILE= This is the complete drive and pathname to the LOG you
| wish to read. Any DOS filename is acceptable, but be
| sure to include the complete drive & path even if it's
| in the directory where NETBULL is started.
|
| LOGTYPE= This tells NETBULL how to read the log. At present, four
| log types are known to NETBULL: TNET, POSTLINK, PCRELAY
| and WILDMAIL. We may add others if there's enough interest.
|
| REFERENCE= If you specify a log type of POSTLINK, PCRELAY or WILDMAIL,
| NETBULL will need to read a REFERENCE FILE to translate the
| log file conference names and numbers into the conference
| names and numbers on your BBS. Check the NETBULL documen-
| tation and then enter the complete drive, path, and filename
| for the reference file here. If the LOGTYPE is TNET, you
| should specify "REFERENCE=NONE"
|
| HUBID= This is used by TNET and by WILDMAIL, but NOT by POSTLINK
| nor PCRELAY. Since TNET lists the name of the HUB in the log,
| you may choose to keep only ONE log file for your various
| TNET imports and exports. If the LOGTYPE is TNET, then you
| must enter the HUBID here. It must match exactly the
| name of the HUB as shown in your TNET log file.
|
| In the case of WILDMAIL, insert the FIDO ID number here,
| for example HUBID=86:8012/3. In this way, you can separate
| each HUB into a separate listing while using only one log.
|
| NETNAME= This is the name of the network as you want it to be shown
| in the display files. An entry may be up to 40 characters
| in length. Any excess will be truncated in order to fit
| the format of the display file.
|
| A total of 19 LOG FILE groups are supported by NETBULL.